• Some MDEVs are known to be incompatible with other MDEVs. If you experience problems, remove unused MDEVs so that only one MDEV is installed on your computer at a time.
• Users who dial into a TCP/IP network or Internet Service Provider (ISP) may have been assigned a router (gateway) address that is not a part of their local subnet. This was an accepted but technically invalid configuration for MacTCP. Open Transport users should not enter a value for the router address or subnet mask; Open Transport/TCP generates correct values for these fields automatically. In unusual circumstances, these supplied values can be overridden using the Administration mode of the TCP/IP control panel.
• If BootP is used over SLIP or PPP for interface configuration, and if BootP returns additional default router addresses, Open Transport will automatically add those addresses to the list of default routers.
• When Open Transport is installed on a computer that previously had MacTCP configured for a server configuration, the initial configuration method—the selection in the “Configure” pop-up menu in the TCP/IP control panel—is set for the use of a BootP server. This default may not be the appropriate choice for you; please verify.
• If your computer was previously configured for MacTCP “server” addressing and you experience connection difficulties using PPP or SLIP after installing Open Transport, follow these steps:
1. Open the TCP/IP control panel.
2. Choose Using PPP Server or Using SLIP from the Configure pop-up menu.
3. Close the TCP/IP control panel, and save changes when prompted.
4. Try connecting again.
• If your computer was previously configured for MacTCP “manual” addressing and you experience connection difficulties using PPP or SLIP after installing Open Transport, follow these steps:
1. Open the TCP/IP control panel.
2. Choose Manual from the Configure pop-up menu.
3. Verify that the correct IP address is entered in the Address field.
4. Close the TCP/IP control panel, and save changes when prompted.
5. Open the configuration utility supplied with your SLIP or PPP software, and verify that it also reflects the correct IP address in the appropriate location. Refer to the documentation supplied with your SLIP or PPP software for further information on how to enter an IP address, and how to save an updated configuration.
6. Try connecting again.
Note: In MacPPP’s ConfigPPP control panel, this setting is entered in the IPCP dialog box. Refer to the documentation that came with MacPPP or FreePPP for additional information.
Known limitations and other issues
• The AppleTalk control panel displays separate printer and modem ports on the PowerBook 190. LocalTalk will only work correctly when the modem port is selected in the AppleTalk control panel.
• The software that dims the screen of PowerBook Duo computers when the PowerBook is docked and idle is not compatible with Open Transport. Use a third-party screen saver in place of the Apple-provided module.
• In some cases, on a PowerBook 190 configured to use the Infrared Port in the AppleTalk “Connect via” pop-up menu, networking services may become disabled following a sleep/wake or restart. If this happens, try putting the computer to sleep and waking it up again, or use the AppleTalk control panel to temporarily select the modem/printer port before switching back to the infrared port.
• On a IIfx or a Quadra 950, Open Transport can only use the “compatible mode” setting in the Serial Switch control panel. Don’t use the “faster mode” setting with LocalTalk.
• On 68030 and 68040 computers, changes in AppleTalk configurations can cause systems running Meeting Maker 3.5 or 3.5.1 to crash. This can occur when changing AppleTalk links, turning AppleTalk off, or bringing ARA connections up or down. This problem will occur on classic networking as well. Apple is working with ON Technology to resolve this problem.
• Open Transport generally requires more memory (RAM) than MacTCP. To conserve memory, you might try some of the following:
- Rename or re-order one or more third-party system extensions (INITs), to change the order in which memory is allocated when your computer starts up. If you use extensions from Global Village, try renaming those extensions so that they load last.
- Especially on PowerPC-based computers, turn on virtual memory. This may affect performance.
• When TCP/IP is set to “Load only when needed” (in the control panel’s Options window), “pinging” an Open Transport workstation will fail if TCP/IP is not currently being used. To make sure your computer is “pingable” at all times, turn off the “Load only when needed” option (open the TCP/IP control panel and click the Options button, then click the “Load only when needed” checkbox to remove the X) and restart your computer.
• When TCP/IP is set to “Load only when needed” (in the control panel’s Options window), the first TCP/IP application opened will cause Open Transport to load into memory. Some older applications don’t cause Open Transport to load, and then report errors similar to those encountered when MacTCP is not installed. If this is a problem, turn off the “Load only when needed” option (open the TCP/IP control panel and click the Options button, then click the “Load only when needed” checkbox to remove the X) and restart your computer.
• The TCP/IP control panel is able to obtain and utilize multiple gateway and name server addresses from DHCP and BootP servers. However, it will currently display only the first one. This should be addressed in a future release.
• Generally, you should turn on the “Load only when needed” option in the TCP/IP control panel when using a modem. If TCP/IP is always loaded ("Load only when needed" is not checked), your modem may attempt to initiate a dialup connection at startup. Some MDEVs require more system heap memory than is available at startup, which may cause the computer to hang. Also, some Internet service providers charge by connect time, so you may be charged for the connection, even if you weren’t using it.
• If you use MacSLIP, you should likewise not configure the MacSLIP control panel to initialize MacSLIP at system startup time. As stated above, this may require more system heap memory than is available at startup, which may cause the computer to hang.
• If you are experiencing problems when using MacSLIP with virtual memory on, increasing your virtual memory size may give you better results. (Use the Memory control panel to increase virtual memory.)
• If you are using Netscape, 16MB or more of built-in memory (RAM) is recommended.
• Some MacTCP-based applications will not function correctly unless the MacTCP DNR file is in its original location at the root level of the System Folder.
• You should only specify use of 802.3 framing in the TCP/IP control panel if you have been directed to do so by your network manager, or if you are sure that all other stations on your network segment, including your IP router(s), are also configured to use 802.3 and not Ethernet version 2.0 framing.
• Claris Emailer version 1.1 v3 or later and Claris Emailer Lite version 1.1 v4 or later is compatible with Open Transport 1.1.2. Earlier versions of Claris Emailer may not be compatible with Open Transport’s “Load only when needed” configuration option. If you experience a system crash 2-3 minutes after quitting Emailer, turn off the “Load only when needed” option. (Open the TCP/IP control panel and click the Options button, then click the “Load only when needed” checkbox to remove the X.)
• The current version of the MacTraceRoute Ethernet LAP does not work on computers running Open Transport.
• NFS/Share versions 1.4.4 or later are compatible with Open Transport.
• When using Netware Client version 5.11 configured for NetwareIP service, the first login may yield a Netware Configuration error message. To avoid this error, open the NetwareIP control panel and change the value under Domain SAP Server (DSS) Retry Attempts from 1 to 2. You can also change OpenTransport TCP/IP control panel to always load TCP/IP into memory (open the TCP/IP control panel, click the Options button, and click the “Load only when needed” box to remove the X).
• eXodus 5.2.2 and later are compatible with Open Transport.
• Versions of Anarchie prior to 1.6 have a data corruption problem when used with Open Transport. Make sure you are using Anarchie 1.6 or later.
• If an Apple Remote Access (ARA) user is on a non-routed, extended (Ethernet) network, and there are devices on the local network with the same network number as devices on the remote network, the user won’t be able to see the local devices. This problem can be fixed by installing a router. Another workaround is to clear the PRAM on the ARA computer. (Hold down the Command, Option, and PR keys simultaneously while starting up the computer). Clearing PRAM causes the computer to start up with a new network number, which should not conflict with the remote network number.
• Daemon 1.0.0 & Daemon Killer 1.0 are not compatible with Open Transport.
• MudDweller 1.2 is not completely compatible with Open Transport. You can open new connections, but the “reconnect” choice does not work correctly.
• The system will crash during launch of NetPresenz if Open Transport TCP/IP is configured to use MacIP and the selected zone has no MacIP server.
• Current versions of VersaTerm SLIP are not compatible with Open Transport.
• Problems can occur with old versions of the KeyServer package from Sassafras Software when TCP/IP is configured to “Load only when needed” (in the control panel’s Options window). Contact Sassafras for the latest revisions at <http://www.sassafras.com>.
• The combination of Open Transport 1.1.2, LocalTalk Bridge 2.1f2, Global Village Toolbox and GlobalFax extensions causes a crash. This also happens when using classic networking. The workaround is to move the LocalTalk Bridge file to the Extension folder, renaming it to “aLocalTalk Bridge.” You can make an alias and rename the alias as desired. Put the alias wherever you want, including the Control Panels folder. This will allow the LocalTalk Bridge to load before Global Village and avoid the cause of the crash.
• To use the CSI Hurdler serial card with Open Transport, contact CSI to get a copy of their preference file patch. This will enable the card to be compatible with Open Transport 1.1.2.
• After installing Open Transport 1.1.2 over a network while using Classic AppleTalk, open the Open Transport 1.1.2 AppleTalk control panel. If you are not using an infrared device, open the “Connect via” pop-up menu and choose Serial Port.
• The current official release of the MPW shell will hang the system when used with virtual memory and Open Transport. When using the MPW shell and Open Transport, turn off virtual memory. The ETO #21 pre-release MPW shell, version 3.4.2b2, fixes this problem.
• Apple is working on acceptable solutions to the following known problems for future versions of Open Transport:
- TCP "Ping of Death"
- TCP "Denial of Service Attacks"
- Differences in WebStar throughput using Open Transport versus MacTCP over low speed lines.
System 7.5.3 notes
• System 7.5.3 includes both classic and Open Transport networking.
• The Network Software Selector (NSS) utility, included in the Apple Extras folder with System 7.5.3, provides an easy way to specify either classic or Open Transport networking. The computer must be restarted for a change to take effect.
• During system startup, System 7.5.3 checks for the stored preference for networking software. The load process then causes the appropriate control panels—“Network” and “MacTCP” for classic networking, “AppleTalk” and “TCP/IP” for Open Transport—to become visible. Those control panels associated with the disabled network software are hidden.
• Prior to installing OT 1.1, it was technically possible to install the older MacTCP on a computer running Open Transport. With OT 1.1 and later this is no longer possible.
• If it becomes necessary to reinstall MacTCP or the Network System Installer (NSI) on a 68030, 68040, or NuBus PowerPC-based computers running System 7.5.3 and Open Transport, you must first use NSS to specify classic networking and restart. After restarting, MacTCP and the other components of classic networking are visible.
• If you have a PCI-based computer connected to a Novell Netware network and are using the Netware 5.1 client software, you should also install the Ethernet Compatibility extension version 1.0.3. This extension is available only through a Custom Install from the System Update 2.0 installer, selecting the Ethernet Driver Update. This corrects a problem that could cause your system to crash at shutdown when using MacIPX. However, there will be a two-minute delay in shutting down the computer.
• Network Time v2.0.1 is not compatible with the AutoPower On/Off control panel version 1.0 on a NuBus Power Macintosh with Open Transport. To use Network Time v2.0.1, remove the AutoPower On/Off control panel.
System 7.5.5 notes
The System 7.5.5 Update is a set of system software enhancements that improves the reliability and performance of all Macintosh and Mac OS-compatible computers running system software version 7.5.3.
• System 7.5.5 Update includes improved reliability when using Ethernet and virtual memory. If you use Ethernet and have virtual memory turned on, you may have experienced problems transferring large files over Ethernet. System 7.5.5 Update fixes this problem.
• System 7.5.5 Update includes improvements in LocalTalk that provide:
• better reliability on Macintosh 5400 series computers
• better performance when using some third-party infrared software products
• System 7.5.5 Update includes improved reliability when using Ethernet on the Macintosh 5400 and 6400 series computers.
• System 7.5.5 Update includes improved stability when using a shared printer on a network. If your computer crashed when you were trying to use a shared printer on a network, System 7.5.5 Update fixes the problem.
• If you install Apple Telecom 3.0 or Express Modem 3.0 after installing the System 7.5.5 Update you will not be able to switch on your Express Modem. To fix this incompatibility, run the System 7.5.5 Update again. The System 7.5.5 Update updates your Express Modem 3.0 to Express Modem 3.0.1.
• There is a known incompatibility with the Sagem GeoPort ISDN Adapter 1.0 and System 7.5.5 Update, resulting in the inability to use the GeoPort ISDN Adapter. Sagem has been contacted about this problem and is working on a solution. If you have a Sagem GeoPort ISDN Adapter, you should not install the System 7.5.5 Update until Sagem resolves the conflict. For more information, visit the Sagem web site at <http://www.satusa.com> or e-mail sathelp@satusa.com.
• Programs use slightly more memory
If you are having new problems with programs reporting that they do not have enough memory, System 7.5.5 Update may require programs to use an additional 23K of memory. To fix the problem:
1. Quit the program if it is open.
2. Click the program's icon to select it.
3. Open the File menu and choose Get Info.
4. In the Info window, increase the value in the "Preferred size" box by 23.
5. Close the window.
• Launching Timbuktu on System Update 7.5.5 with VM "on" from the Timbuktu menu may cause a crash. Workaround is to launch Timbuktu from the Finder instead.
Apple, the Apple logo, AppleShare, AppleTalk, LaserWriter, LocalTalk, MacTCP, Performa, Power Macintosh, PowerBook, and PowerBook Duo are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. At Ease is a trademark of Apple Computer, Inc. NuBus is a trademark of Texas Instruments.PowerPC is a trademark of International Business Machines Corporation, used under license therefrom. All other product names are trademarks or registered trademarks of their respective holders. Mention of non-Apple products is for information purposes and constitutes neither an endorsement nor a recommendation. Apple assumes no responsibility with regard to the selection, performance, or use of these products.
